Facilitating mobile device payments using product code scanning

ABSTRACT

Mobile device payments using barcodes are displayed on mobile devices and scanned by merchants at checkout counters. When a customer is ready to tender a payment to a merchant, instead of using a credit card, cash, or check, the customer activates an application on his mobile device. The mobile device includes or obtains information about the payment system of this merchant. Furthermore, the mobile device includes or obtains information about the customer/mobile device user and then uses these two pieces of information to generate and display a barcode that encodes customer payment information specific to this merchant. The barcode is scanned by one scan or one touch at the checkout counter and processed to retrieve customer records from a database of the payment processing system. These records are then used to transfer funds between the merchant and customer, obtain discounts, and/or perform other retail transactions.

RELATED PATENT APPLICATION AND INCORPORATION BY REFERENCE

This application is a continuation-in-part of U.S. patent applicationSer. No. 13/185,491, entitled ‘FACILITATING MOBILE DEVICE PAYMENTS USINGPRODUCT CODE SCANNING,’ filed on Jul. 18, 2011, and U.S. patentapplication Ser. No. 14/979,613, “ONE-SCAN AND ONE-TOUCH PAYMENT ANDBUYING USING HAPTIC CONTROL VIA MESSAGING AND CALLING MULTIMEDIA SYSTEMON MOBILE AND WEARABLE DEVICE, CURRENCY TOKEN INTERFACE, POINT OF SALEDEVICE, AND ELECTRONIC PAYMENT CARD’, filed on Dec. 28, 2015, and U.S.patent application Ser. No. 14/957,644, entitled ‘SYSTEMS AND METHODSFOR MOBILE APPLICATION, WEARABLE APPLICATION, TRANSACTIONAL MESSAGING,CALLING, DIGITAL MULTIMEDIA CAPTURE AND PAYMENT TRANSACTIONS’, filed onDec. 3, 2015, which is Continuation-in-Part of U.S. patent applicationSer. No. 14/815,988, entitled ‘SYSTEMS AND METHODS FOR MOBILEAPPLICATION, WEARABLE APPLICATION, TRANSACTIONAL MESSAGING, CALLING,DIGITAL MULTIMEDIA CAPTURE AND PAYMENT TRANSACTIONS’, filed on Aug. 1,2015, which claims priority to U.S. patent application Ser. No.12/749,412, entitled ‘EFFICIENT TRANSACTIONAL MESSAGING BETWEEN LOOSELYCOUPLED CLIENT AND SERVER OVER MULTIPLE INTERMITTENT NETWORKS WITHPOLICY BASED ROUTING’, filed on Mar. 29, 2010, and U.S. patentapplication Ser. No. 14/034,509, entitled ‘EFFICIENT TRANSACTIONALMESSAGING BETWEEN LOOSELY COUPLED CLIENT AND SERVER OVER MULTIPLEINTERMITTENT NETWORKS WITH POLICY BASED ROUTING’, filed on Sep. 23,2013, which is Continuation-in-Part of U.S. patent application Ser. No.10/677,098, entitled ‘EFFICIENT TRANSACTIONAL MESSAGING BETWEEN LOOSELYCOUPLED CLIENT AND SERVER OVER MULTIPLE INTERMITTENT NETWORKS WITHPOLICY BASED ROUTING’, filed on Sep. 30, 2003, which claims priority toU.S. Provisional Patent Application No. 60/415,546, entitled ‘DATAPROCESSING SYSTEM’, filed on Oct. 1, 2002, which are incorporated hereinby reference in its entirety.

SUMMARY OF INVENTION

(1) Field of the Invention

This application relates generally to data processing, and morespecifically to methods and systems for one-touch and one-scan buyingand paying performed via a mobile and wearable device.

(2) Background

Mobile payments generally refer to payment operations performed via amobile or wearable device. The operations performed via mobile andwearable devices may include electronic commerce transactions, retailpurchasing, micropayments, and other daily payments. Mobile payments mayutilize credit cards, debit cards, gift cards, and virtual currencies.While mobile payments facilitate and stimulate the trade, the procedureof providing financial details and authenticating of identity may betedious and time-consuming. Therefore, the convenience of mobilepayments for daily micropayments is hindered.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Provided are computer implemented methods and systems for messaging,calling, and one-touch and one-scan payments and buying via a mobile andwearable device. Using the methods or systems described herein a usermay perform facilitated electronic payments from any location. For thispurpose, the user may register with the messaging, calling, andone-touch and one-scan payment and buying system. During theregistration the user may provide his financial information. Thefinancial information may include bank account information, credit cardinformation, debit card information, gift card information, prepaid cardinformation, insurance account information, merchant accountinformation, mobile currency information, digital money account, SDKpayment information, in-app payment information, social networkingpayment information, prepaid card information, API payment information,mobile account payment information, mobile currency information, and soforth. When required, the user may activate a haptic control associatedwith a messaging, calling, and one-touch and one-scan payment and buyingsystem. The haptic control may be displayed over the video output of thedevice and overlap other applications or pages. The haptic control mayprovide for mode selection elements associated with a payment mode, amessaging mode, a calling mode, and a multimedia capture mode. Throughthe haptic control the messaging, calling, and one-touch and one-scanpayment and buying system may receive the selection of the payment modevia the mode selection elements of the haptic control from a user. Uponthe selection, context may be extracted from the display of the mobileand wearable device. Based on the context, a payment transaction typewhich the user intends to perform may be determined. The paymenttransaction type may include a payment receiving transaction and apayment sending transaction. Based on the determining, a transactionrequest may be generated using data of the extraction and the financialinformation of the user provided during the registration.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe drawings set forth in detail certain illustrative features of theone or more aspects. These features are indicative, however, of but afew of the various ways in which the principles of various aspects maybe employed, and this description is intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are illustrated by way of example and not limitation in thefigures of the accompanying drawings, in which like references indicatesimilar elements and in which:

FIG. 1 is a block diagram showing an environment within which a systemfor messaging, calling, and one-touch and one-scan payment and buyingsystem and a method of using thereof can be implemented, in accordancewith an example embodiment.

FIG. 2 is a block diagram showing various modules of the messaging,calling, and one-touch and one-scan payment and buying system, inaccordance with certain embodiments.

FIG. 3 is a flow chart illustrating a method for messaging, calling, andone-touch and one-scan payments and buying via a mobile and wearabledevice, in accordance with certain embodiments.

FIG. 4 is a block diagram illustrating a haptic control, in accordancewith certain embodiments.

FIG. 5 is a block diagram illustrating a one-touch and one-scan paymentand buying operation using the messaging, calling, and one-touch andone-scan payment and buying system, in accordance with certainembodiments.

FIG. 6 is a block diagram showing various modules of a messaging,calling, and one-touch and one-scan payment and buying mobile serviceusing a one-touch button, in accordance with certain embodiments.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth inorder to provide a thorough understanding of the presented concepts. Thepresented concepts may be practiced without some or all of thesespecific details. In other instances, well known process operations havenot been described in detail so as to not unnecessarily obscure thedescribed concepts. While some concepts will be described in conjunctionwith the specific embodiments, it will be understood that theseembodiments are not intended to be limiting.

Various computer implemented methods and systems for messaging, calling,and one-touch and one-scan payments and buying via a mobile and wearabledevice are described herein. The described system enables a user to makeand request payments using a mobile device by one touch. To facilitateaccess to the system, the user initiates the system. When the system isinitiated, a one-touch button is shown on a display of the mobile deviceon top of other applications and/or widgets. The one-touch button has atleast three controls to activate messaging, calling, or one-touch andone-scan payment. One-touch payment control, when activated, determineswhether the user intends to make a payment or to request a payment bythe context in view on the display and performs the correspondingoperation. Such accelerated payment procedure may facilitate electronicpurchases and stimulate electronic trade.

Referring now to the drawings, FIG. 1 illustrates an environment 100within which messaging, calling, and one-touch and one-scan payment andbuying system and a method of using thereof can be implemented. Theenvironment 100 may include a user 120, a client device 130, network110, a messaging, calling, and one-touch and one-scan payment and buyingsystem 200. On a user request, the messaging, calling, and one-touch andone-scan payment and buying system 200 may provide a haptic control on adisplay of the client device 130. The haptic control may include, forexample, a one-touch button. The client device 130

Via the haptic control, the user 120 may exchange messages 160 with arecipient 140, make calls 170, and perform or request one-touch andone-scan payments 180. The messages 160, calls 170, and one-touch andone-scan payments 180 are transmitted to the system 200 and further tothe recipient 140 or payee (not shown) via the network 110 using theclient device 130

The network 110 may include the Internet or any other network capable ofcommunicating data between devices. Suitable networks may include orinterface with any one or more of, for instance, a local intranet, a PAN(Personal Area Network), a LAN (Local Area Network), a WAN (Wide AreaNetwork), a MAN (Metropolitan Area Network), a virtual private network(VPN), a storage area network (SAN), a frame relay connection, anAdvanced Intelligent Network (AIN) connection, a synchronous opticalnetwork (SONET) connection, a digital T1, T3, E1 or E3 line, DigitalData Service (DDS) connection, DSL (Digital Subscriber Line) connection,an Ethernet connection, an ISDN (Integrated Services Digital Network)line, a dial-up port such as a V.90, V.34 or V.34bis analog modemconnection, a cable modem, an ATM (Asynchronous Transfer Mode)connection, or an FDDI (Fiber Distributed Data Interface) or CDDI(Copper Distributed Data Interface) connection. Furthermore,communications may also include links to any of a variety of wirelessnetworks, including WAP (Wireless Application Protocol), GPRS (GeneralPacket Radio Service), GSM (Global System for Mobile Communication),CDMA (Code Division Multiple Access) or TDMA (Time Division MultipleAccess), cellular phone networks, GPS (Global Positioning System), CDPD(cellular digital packet data), RIM (Research in Motion, Limited) duplexpaging network, Bluetooth radio, or an IEEE 802.11-based radio frequencynetwork. The network 110 can further include or interface with any oneor more of an RS-232 serial connection, an IEEE-1394 (Firewire)connection, a Fiber Channel connection, an IrDA (infrared) port, a SCSI(Small Computer Systems Interface) connection, a Universal Serial Bus(USB) connection or other wired or wireless, digital or analog interfaceor connection, mesh or Digi® networking. The network 110

FIG. 2 is a block diagram showing various modules of the messaging,calling, and one-touch and one-scan payment and buying system 200, inaccordance with certain embodiments. The system 200 may comprise aprocessor 202 a database 204, and a haptic control 206. The processor202 may include a programmable processor, such as a microcontroller,central processing unit (CPU), and so forth. In other embodiments, theprocessor 202 may include an application-specific integrated circuit(ASIC) or programmable logic array (PLA), such as a field programmablegate array (FPGA), designed to implement the functions performed by thesystem 200. Thus, the processor 202 may provide a haptic controlassociated with a messaging, calling, and one-touch and one-scan paymentand buying system. The haptic control may be represented, for example,by a one-touch button shown on a display of a mobile and wearabledevice. The haptic control may overlap other visual elements on thedisplay so that the haptic control was always visible for the user andnot hidden by other screens. In some embodiments, the haptic control 206may be integrated with a mobile application associated with the mobileand wearable device and/or the system 200. The haptic control mayprovide mode selection elements associated with a payment mode, amessaging mode, a calling mode, and multimedia capture mode. Theprocessor 202 may further receive the selection of the payment mode viathe mode selection element of the haptic control 206 from a user. Whenthe payment mode is selected, the processor may extract context from thedisplay of the mobile and wearable device. The context may includeinformation on a web page, an application screen, or a message in viewon the display. For example, the context may include a check-out page ofan online shop. Based on the context, the processor 202 may determine apayment transaction type (i.e. a payment receiving transaction or apayment sending transaction) which the user intends to perform. For thispurpose, the processor 202 may parse the context and identify key wordsassociated with a specific payment transaction type. For instance, thepayment sending transaction may be associated with the following keywords: ‘check-out,’ ‘cart,’ and so forth. According to the determinedtransaction, a transaction request may be sent to a financialinstitution using the information extracted from the context andfinancial information of the user stored in the database 204

The transaction request may be sent without requesting financialinformation, authorizing, or confirmations from the user. However, insome embodiments, the user, with the help of options of the system 200

Furthermore, the user may select a messaging mode via the mode selectionelements of the haptic control 206. Then, the processor may provide amessaging interface on the display of the mobile and wearable device.When a message and a choice of a recipient is received from the user viathe messaging interface, the processor 202

If the calling mode is selected via the haptic control 206, theprocessor 202 may provide a calling interface on the display of themobile and wearable device. Via the calling interface, the processor 202

If the multimedia mode is selected via the haptic control 206, theprocessor 202 may initiate one or more sensors to capture multimedia toobtain captured multimedia. The processor 202 may analyze a duration ofthe single touch to the section element of the one-touch buttonassociated with the multimedia capture mode. Based on the analysis, theprocessor 202

FIG. 3 is a flow chart illustrating a method 300 for messaging, calling,and one-touch and one-scan payments and buying via a mobile and wearabledevice, in accordance with some example embodiments. The method 300 maybe performed by logic that may comprise hardware (e.g., dedicated logic,programmable logic, and microcode), software (such as software run on ageneral-purpose computer system or a dedicated machine), or acombination of both. In one example embodiment, the processing logicresides at the system 200 for providing compensation for using a mobilepayment service, and the various elements of the system 200 can performthe method 300

As shown in FIG. 3, the method 300 may commence at operation 302 withreceiving payment information associated with a user. The paymentinformation may be also associated with a mobile payment account of theuser in a messaging, calling, and one-touch and one-scan payment andbuying system. At operation 304, a unique code encoding the paymentinformation is generated. The unique code is provided to the user atoperation 306

At operation 308

At operation 310, a selection of the payment mode via the mode selectionelements of the haptic control is received from the user. Upon theselection, context is extracted from the display at operation 312.Information from the screen in view on the mobile and wearable deviceand be captured and analyzed to identify the context. Based on thecontext, a payment transaction type to be performed may be determined atoperation 314

Based on the determining of the payment transaction type, a transactionrequest associated with the determined payment transaction type may besent at operation 316

If the transaction request is associated with the payment sendingtransaction, a deposit amount associated with the payment sendingtransaction related to the user may be received at operation 318.Further, at operation 320

Furthermore, if the messaging mode is selected via the haptic control,the system 200 of FIG. 2

If the calling mode is selected, a calling interface may be provided tothe user. The user may select a call recipient in his contacts and makea call request. The system 200 may receive the call request from theuser. Based on the call request, the system 200

On selection of the multimedia mode, one or more sensors may beinitiated to capture multimedia to obtain captured multimedia. Aduration of the single touch to the section element of the one-touchbutton associated with the multimedia capture mode may be analyzed.Based on the analysis, a type of the captured multimedia may bedetermined: an image and a video recording. When the type if determined,the captured multimedia may be recorded to the database according to thetype determined based on the duration. For instance, if the duration ofthe single touch to the section element of the one-touch buttonassociated with the multimedia capture mode is one second, an image isrecorded to the database, if the duration is more than one second, avideo recording may be stored to the database.

In an example embodiment, the data of the payment card may be storedinto a cloud network. In some embodiments, the data of the payment cardmay be stored in the cloud network as a token.

In some embodiments, the transaction request may include a unique codeassociated with the user. The unique code may encode at least bankaccount information of the user and a payment amount. In furtherembodiments, the unique code may be displayed on the mobile and wearabledevice for scanning by the merchant.

In a further example embodiment, the system 200 may receive product databased on scanning of the product data by the mobile and wearable deviceassociated with the user. The product data may be associated with one ormore products.

The system 200 may determine that the total price for the one or moreproducts exceeds a predetermined price.

In some embodiments, the transaction request may include at least a userphone number. In such a case, the payment sending transaction mayinclude sending a payment from a phone account of the user to a merchantaccount.

In further embodiments, the payment receiving transaction and thepayment sending transaction may be performed by pairing of the mobileand wearable device and a merchant device using a reader. The reader maybe connected to the merchant device and plugged into the mobile andwearable device.

Thus, one-touch and one-scan payment and buying features may improvebuying experience for customers and merchant. Additionally, for the userthat pays and buys products and services using the mobile applicationassociated with one-touch and one-scan payment and buying, the number oftaps and times the user is required to enter a user login(identification number) and a password for future purchases may beminimized.

In some embodiments, upon launching of the at least one mobileapplication by the user, a list of payment cards may be provided forselection by the user. The payment cards may be associated with one ormore of the following: a bank account, a bank mobile account, a serviceprovider account, a digital currency, a universal national currencytoken interface, a national digital currency, an electric payment card,and the like. Upon the selection, a token may be sent to the mobile andwearable device. The token may be associated with a selected paymentcard, and further payments may be performed using the token.

FIG. 4 is a block diagram 400 illustrating a haptic control, inaccordance with certain embodiments. The haptic control 414 may be shownon the display 410 of the mobile and wearable device 412. The hapticcontrol may include one or more mode selection elements. The modeselection elements may include a messaging mode 402, a calling mode 404,and a payment mode 406. A user 408 may give a haptic command (e.g.touch) to select a desired mode.

The transaction request may be generated using data of a mobileapplication or a page from which the payment mode is activated. Forexample, the user may activate the payment mode from a purchase page ofan online store. The payment may be immediately initiated withoutrequesting further details. Data of a payment recipient and a paymentamount may be received from the actual page or application and financialinformation of the user may be stored in the database of the messaging,calling, and one-touch and one-scan payment and buying system 200. Theuser financial information may be provided by the user duringregistration with the messaging, calling, and one-touch and one-scanpayment and buying system 200.

Alternatively, the transaction request may be generated using data of apage associated with billing In that case, the system 200 may generate apayment request using information extracted from the page as well as thefinancial information of the user stored in the system 200.

Transactions can be associated with transactional payments based onUnstructured Supplementary Service Data (USSD) or Short Message Service(SMS), direct operator billing, credit card mobile payments, onlinewallets, QR code payments, contactless near field communication (NFC),cloud-based mobile payments, audio signal-based payment, Bluetooth LowEnergy (BLE) signal beacon payment, in-application payment, SDK payment,API payment, social networking payment, and direct carrier/bankco-operation.

Contactless NFC may be used to receive data for the payment request. Forexample, when the one touch and one-scan payment mode is selected, theuser may make a payment for purchases in physical stores ortransportation services. The mobile and wearable device may be equippedwith a smart card. When a user waves the mobile and wearable device neara radar module, a payment is made. In some cases, the payment mayrequire authentication. The NFC payment could be deducted from a prepaidaccount or changed to a mobile or band account directly. NFC payment mayinclude displaying a barcode on the mobile device screen for mobilepayment. The payment barcode can include one or more of the following: alinear barcode, a two-dimensional barcode, a three-dimensional barcode,a machine readable code, and so forth.

The audio channel of the mobile phone may be another wireless interfacethat is used to receive data for a transaction request. Chip, ultrasound and acoustic features of the mobile and wearable device maysupport mobile payments. Near sound data transfer (NDST), data overvoice and NFC produce audio signatures that the mobile phone can pick upto enable electronic transactions.

In some embodiments, the payment receiving transaction and the paymentsending transaction are performed using a NFC. The NFC may be used topair the mobile and wearable device and a merchant device by bringingthe mobile and wearable device into proximity to the merchant device.The mobile and wearable device and the merchant device may be connectedto a cloud network. The financial data and authorizing data associatedwith the user may be stored in the cloud network. In an exampleembodiment, upon pairing the mobile and wearable device with themerchant device, a Bluetooth connection between the mobile and wearabledevice and the merchant device may be established. The payment receivingtransaction and the payment sending transaction may include at least apear-to-pear transaction.

In some embodiments, a beacon mobile payment sends out a Bluetooth LowEnergy (BLE) signal to anyone or any device with mobile application totransfer payment data and get electronic receipt. When a customer checksin, their picture and name may pop up on the retailer's point-of-salesystem, when a sales associate at the store totals a bill on a cashregister or a card-reading terminal, the beacon mobile payment usergives verbal confirmation to the associate, who matches the customerwith the picture on the POS screen and concludes the transaction.

FIG. 5 is a block diagram illustrating a one-touch payment operation 500using the messaging, calling, and one-touch and one-scan payment system,in accordance with certain embodiments. The user selects a payment mode504 using a one-touch button 502 (i.e. haptic control). The userselection may be transmitted to the system 200, and the system maydetermine information on a page 506 in view on the display. The system200 may automatically provide financial information of the user on thepage 506

FIG. 6 is a block diagram showing various modules of a messaging,calling, and one-touch payment and buying mobile platform shown as amessaging, calling, and one-touch payment mobile service 600 using aone-touch button 608, in accordance with certain embodiments. Themessaging, calling, and one-touch payment mobile service 600 may includea central processing unit (CPU) 604, for example, associated with aremote server 602, a database 606 storing financial information of auser, and a one-touch button 608 presented on a device of the user. TheCPU 604 may provide the one-touch button 608 on a display of a mobileand wearable device. The one-touch button 608 may overlap other visualelements on the display. The CPU 604 may receive a selection of thepayment mode via the mode selection elements of the one-touch button 608from a user. The selection may include a single touch of the user to theone-touch button 608. Upon the selection, the CPU 604 may extractcontext from the display of the mobile and wearable device to determinea payment transaction type which the user intends to perform. Based onthe determining, the CPU 604 may send a transaction request to afinancial institution using the extraction and financial data stored inthe database 606

In some embodiments, the user may select one of the stored paymentaccounts to perform a payment. Authentication may be made when the useraccesses the messaging, calling, and one-touch payment mobile service600

Furthermore, using the messaging, calling, and one-touch payment mobileservice 600 the user may create automatic payments. For example, theuser may give instructions to transfer $1 to a specific account everyweek day at 1:25 PM. The messaging, calling, and one-touch paymentmobile service 600 may receive the instructions and automaticallyperform the payment according to the instructions. After a predefinedperiod, for example, after one month, or every week, or every year, themessaging, calling, and one-touch payment mobile service 600.

Thus, various systems and methods for messaging, calling, and one-touchand one-scan payments and buying via a mobile and wearable device havebeen described. Although embodiments have been described with referenceto specific example embodiments, it will be evident that variousmodifications and changes may be made to these embodiments withoutdeparting from the broader spirit and scope of the system and methoddescribed herein. Accordingly, the specification and drawings are to beregarded in an illustrative rather than a restrictive sense.

What is claimed is:
 1. A computer implemented method for facilitatingmobile device transactions using a mobile and wearable device of acustomer from a customer payment account to merchant accounts ofmerchants, the method comprising: reading product codes of correspondingproducts using the mobile and wearable device, wherein merchantidentification information is encoded into each of the product codes andextracted by the mobile and wearable device, and wherein the productcodes correspond to products sold by different merchants havingdifferent corresponding merchant identification information encodedtherein; based on the reading, providing the merchant identificationinformation on a customer interface of the mobile and wearable device,in accordance with a payment processing system comprising a plurality ofthe merchants, the merchant identification information identifying amerchant in the payment processing system and corresponding merchantaccount; transmitting, from the mobile and wearable device, customeridentification information of the customer to the payment processingsystem; transmitting from the mobile and wearable device, the productcodes to the payment processing system; subsequent to the transmissions,retrieving customer payment information associated with the customerusing the customer identification information and the merchantidentification information by the payment processing system, thecustomer payment information corresponding to the customer paymentaccount maintained at the payment processing system associated with themerchant and further including a name of the customer, a customeraccount number of a financial account, and an amount of available funds;based on the customer identification information and the merchantidentification information, retrieving customer records by the paymentprocessing system, the customer records being maintained at the paymentprocessing system, the customer records including at least discountinformation associated with the customer and loyalty program informationassociated with the customer; in response to the transmittingtransmissions and the retrieving, generating, by the payment processingsystem, a barcode encoding the customer payment information and thecustomer records, specific to the merchant, said barcode generated usingthe merchant identification information and the customer identificationinformation; transmitting, by the payment processing system, the barcodeto the mobile and wearable device; displaying the barcode on a screen ofthe mobile device, wherein the displayed barcode is scanned by a barcodescanner at a checkout counter of the payment processing system; and inresponse to the scanning, transferring payment from the customer paymentaccount to each of the merchant accounts corresponding to the merchantidentification information encoded into the product codes; providing tothe customer, by the processor, in response to the receiving paymentinformation and authentication information of the customer, a uniquecode encoding account information and a payment amount and a hapticcontrol, wherein the haptic control comprises a graphic image shown on adisplay of the mobile and wearable device overlapping other visualelements on the display, the haptic control providing mode selectionelements associated with a payment mode, a messaging mode, a callingmode, and a multimedia capture mode, wherein the haptic control iscompatible with other programs installed on the mobile and wearabledevice associated with the payment mode, the messaging mode, the callingmode, and the multimedia capture mode, and providing a plurality ofstored payment cards for selection by the customer to use in at leastthe payment mode, the haptic control facilitating online transactionsnot completed at the checkout counter; superimposing, by the processor,the haptic control on the display of the mobile and wearable device ontop of all content displayable of the mobile and wearable device fromthe other programs, and using the haptic control within the otherprograms to facilitate at least one of performing payments, messaging,and calling associated with the payment mode, the messaging mode, thecalling mode, and the multimedia capture mode of the mobile and wearabledevice; receiving, by the processor, a selection of the payment mode viathe mode selection elements of the haptic control from the customer,wherein the selection of the payment mode includes a single touching ofthe mode selection elements associated with the payment mode; upon theselection, automatically extracting, by the processor, context from atleast one of the other installed programs from the display of the mobileand wearable device, wherein the context comprises one or more of apayment recipient, a payment account, a sender account, and a paymentamount extracted from a web page, an application screen, or a message inview on the display; based on the context, automatically determining, bythe processor, a payment transaction type which the customer intends toperform, wherein the payment transaction type includes a paymentreceiving transaction and a payment sending transaction; when thedetermined payment transaction type is the payment receivingtransaction, automatically sending a transaction request to a financialinstitution without requesting financial information, authorizing, orconfirmations, wherein the transaction request associated with thepayment receiving transaction includes at least the unique code, andreceiving a payment from the financial institution, wherein subsequentto the selection of the payment mode, the payment receiving transactionis automatically performed with no further input by the customer afterthe selection; when the determined payment transaction type is thepayment sending transaction, calculating, by the processor, a depositamount associated with the payment sending transaction related to thecustomer and sending a transaction request associated with the paymentsending transaction to the financial institution, wherein thetransaction request associated with the payment sending transactionincludes at least the unique code, wherein the deposit amount amounts toa predetermined percent from the payment amount, wherein the depositamount is associated with the mobile payment account of the customer,and sending a payment from the customer to the financial institution,wherein subsequent to the selection of the payment mode, the paymentsending transaction is automatically performed with no further input bythe customer after the selection; receiving, by the processor, anotification about a further payment sending transaction of the customervia the mobile payment service, the notification including at least theunique code and a payment amount of the further payment sendingtransaction; providing at least one of a compensation, a rebate, acashback, and a reward from the deposit amount to the customer, the atleast one of the compensation, the rebate, the cashback, and the rewardbeing associated with the payment amount associated with the furtherpayment sending transaction and not associated with the payment sendingtransaction, wherein the at least one of the compensation, the rebate,the cashback, and the reward amounts to the predetermined percent fromthe payment amount; receiving, by the processor, a selection of themessaging mode via the mode selection elements of the haptic controlfrom the customer, wherein the selection of the messaging mode includesa single touching of the mode selection elements associated with themessaging mode; when the selection of the messaging mode is received,providing, by the processor, a messaging interface on the display of themobile and wearable device to enable the customer to provide, via themessaging interface, a message and a selection of a recipient, theselection of the messaging mode being performed via touching the modeselection elements associated with the messaging mode by the customer;upon receipt of the message and the selection of the recipient, sending,by the processor, the message to the recipient via a data network;receiving, by the processor, a selection of the calling mode via themode selection elements of the haptic control from the customer, whereinthe selection of the calling mode includes a single touching of the modeselection elements associated with the calling mode; when the selectionof the calling mode is received, providing, by the processor, a callinginterface on the display of the mobile and wearable device, to enablethe customer to provide, via the calling interface, a call recipient,the selection of the calling mode being performed via touching the modeselection elements associated with the calling mode by the customer; andupon receipt of the call recipient, performing, by the processor, a callwith the call recipient via the data network; and when a selection ofthe multimedia capture mode is received, initiating with the processor,one or more sensors to capture multimedia; analyzing with the processor,the single touch to determine a duration of the single touch, and basedon the analysis, determine a type of multimedia to be recorded, whereinthe type of multimedia includes an image and a video recording, andrecording the captured multimedia to the database.
 2. The method ofclaim 1, wherein the financial data and authorizing data associated withthe user is provided by the user during registration and stored in themessaging, calling, and one-touch and one-scan payment and buyingsystem.
 3. The method of claim 1, wherein the determining includesparsing of the context extracted from the display.
 4. The method ofclaim 1, wherein the call is performed via a Voice over InternetProtocol (VoIP) service, the VoIP service being provided via Wi-Fi, 3Gnetwork, 4G network, 5G network, 6G network or upper.
 5. The method ofclaim 1, wherein the call is selected from a group comprising: an audiocall, a video call, and a holographic video call.
 6. The method of claim1, wherein the financial information includes one or more of thefollowing: bank account information, credit card information, debit cardinformation, gift card information, prepaid card information, insuranceaccount information merchant account information, mobile currencyinformation, and digital money.
 7. The method of claim 1, wherein thetransaction request is associated with a virtual currency.
 8. A systemconfigured to perform mobile device transactions using a mobile andwearable device of a customer form a customer account to merchantaccounts of merchants, the system comprising: the mobile and wearabledevice comprising a processor configured to: control reading of productcodes of corresponding merchant products using the mobile and wearabledevice, wherein merchant identification information is encoded into eachof the product codes and extracted by the mobile and wearable device,and wherein the product codes correspond to products sold by differentmerchants having different corresponding merchant identificationinformation encoded therein; provide, via a customer interface of themobile and wearable device, merchant identification information, inaccordance with a payment processing system comprising a plurality ofthe merchants, the merchant identification information identifying amerchant in the payment processing system and corresponding merchantaccount; transmit customer identification information of the customer tothe payment processing system and the product codes to the paymentprocessing system; subsequent to the transmissions, retrieve of customerpayment information associated with the customer using the customeridentification information and the merchant identification informationby the payment processing system, the customer payment informationcorresponding to the customer payment account maintained at the paymentprocessing system associated with the merchant and further including aname of the customer, a customer account number of a financial account,and an amount of available funds; based on the customer identificationinformation and the merchant identification information, retrievecustomer records by the payment processing system, the customer recordsbeing maintained at the payment processing system, the customer recordsincluding at least discount information associated with the customer andloyalty program information associated with the customer; in response tothe transmitting transmissions and the retrieving, generate a barcodeencoding the customer payment information and the customer records,specific to the merchant, said barcode generated using the merchantidentification information and the customer identification informationand send said barcode to the mobile and wearable device; display thebarcode on a screen of the mobile device, wherein the displayed barcodeis scanned by a barcode scanner at a checkout counter of the paymentprocessing system; and in response to the scanning, control the transferpayment from the customer payment account to each of the merchantaccounts corresponding to the merchant identification informationencoded into the product codes; the processor being further configuredto: provide, in response to the receiving of the payment information andauthentication information of the customer, a unique code encodingaccount information and a payment amount and a haptic, wherein thehaptic control comprises a graphic image shown on a display of themobile and wearable device overlapping other visual elements on thedisplay, the haptic control providing mode selection elements associatedwith a payment mode, a messaging mode, a calling mode, and a multimediacapture mode, wherein the haptic control is compatible with otherprograms installed on the mobile and wearable device associated with thepayment mode, the messaging mode, the calling mode, and the multimediacapture mode, the haptic control facilitating online transactions notcompleted at the checkout counter; superimpose, the haptic control onthe display of the mobile and wearable device on top of all contentdisplayable of the mobile and wearable device from the other programs,and using the haptic control within the other programs to facilitate atleast one of performing payments, messaging, and calling associated withthe payment mode, the messaging mode, the calling mode, and themultimedia capture mode of the mobile and wearable device; receive, aselection of the payment mode via the mode selection elements of thehaptic control from the customer, wherein the selection of the paymentmode includes a single touching of the mode selection elementsassociated with the payment mode; upon the selection, automaticallyextract, context from at least one of the other installed programs fromthe display of the mobile and wearable device, wherein the context isextracted from a web page, an application screen, or a message in viewon the display; and based on the context, automatically determine, bythe processor, a payment transaction type which the customer intends toperform, wherein the payment transaction type includes a paymentreceiving transaction and a payment sending transaction; when thedetermined payment transaction type is the payment receivingtransaction, automatically send a transaction request to a financialinstitution without requesting financial information, authorizing, orconfirmations, wherein the transaction request associated with thepayment receiving transaction includes at least the unique code, andreceiving a payment from the financial institution, wherein subsequentto the selection of the payment mode, the payment receiving transactionis automatically performed with no further input by the customer afterthe selection; when the determined payment transaction type is thepayment sending transaction, calculate, a deposit amount associated withthe payment sending transaction related to the customer and send atransaction request associated with the payment sending transaction tothe financial institution, wherein the transaction request associatedwith the payment sending transaction includes at least the unique code,wherein the deposit amount amounts to a predetermined percent from thepayment amount, and wherein the deposit amount is associated with themobile payment account of the customer, and send a payment from thecustomer to the financial institution, wherein subsequent to theselection of the payment mode, the payment sending transaction isautomatically performed with no further input by the customer after theselection; receive, a notification about a further payment sendingtransaction of the customer via the mobile payment service, thenotification including at least the unique code and a payment amount ofthe further payment sending transaction; provide at least one of acompensation, a rebate, a cashback, and a reward from the deposit amountto the customer, the at least one of the compensation, the rebate, thecashback, and the reward being associated with the payment amountassociated with the further payment sending transaction and notassociated with the payment sending transaction, wherein the at leastone of the compensation, the rebate, the cashback, and the rewardamounts to the predetermined percent from the payment amount; receive aselection of the messaging mode via the mode selection elements of thehaptic control from the customer, wherein the selection of the messagingmode includes a single touching of the mode selection elementsassociated with the messaging mode; when the selection of the messagingmode is received, provide, by the processor, a messaging interface onthe display of the mobile and wearable device to enable the customer toprovide, via the messaging interface, a message and a selection of arecipient, the selection of the messaging mode being performed viatouching the mode selection elements associated with the messaging modeby the customer; upon receipt of the message and the selection of therecipient, send the message to the recipient via a data network; receivea selection of the calling mode via the mode selection elements of thehaptic control from the customer, wherein the selection of the callingmode includes a single touching of the mode selection elementsassociated with the calling mode; when a selection of the calling modeis received, provide a calling interface on the display of the mobileand wearable device, to enable the customer to provide, via the callinginterface, a call recipient, the selection of the calling mode beingperformed via touching the mode selection elements associated with thecalling mode by the customer; upon receipt of the call recipient,perform a call with the call recipient via the data network; and when aselection of the multimedia capture mode is received, initiate one ormore sensors to capture multimedia; analyze the single touch todetermine a duration of the single touch, and based on the analysis,determine a type of multimedia to be recorded, wherein the type ofmultimedia includes an image and a video recording, and record thecaptured multimedia to the database.
 9. The system of claim 8, whereinthe haptic control is integrated with at least one mobile applicationassociated with the mobile and wearable device, wherein the at least onemobile application is integrated into a software development kit and anoperating system of the mobile and wearable device, wherein theoperating system is selected from a group comprising: iOS, Android, andWindows Phone, wherein, upon launching of the at least one mobileapplication by the user, the user is prompted to log in and asked toprovide a consent that the at least one mobile application initiatesfuture payments on behalf of the user, wherein during further purchasesthe at least one mobile application is launched by default without aneed for a further action from the user to initiate launching of the atleast one mobile application, the further action including entering alogin and a password by the user, wherein the at least one mobileapplication is associated with performing payments and buying productsor services in the Internet.
 10. The system of claim 9, wherein uponlaunching of the at least one mobile application by the user, a list ofpayment cards is provided for selection by the user, the payment cardsbeing associated with one or more of the following: a bank account, abank mobile account, a service provider account, a digital currency, auniversal national currency token interface, a national digitalcurrency, and an electric payment card; wherein upon the selection, atoken is sent to the mobile and wearable device, the token beingassociated with a selected payment card, wherein further payments areperformed using the token.
 11. The system of claim 8, wherein theprocessor is further configured to download applications, receive andset text, video, and multimedia data.
 12. The system of claim 8, whereinthe processor is further configured to: authenticate an identity of theuser, the authenticating including one or more of a passwordauthentication, a voice authentication, and a biometric authentication,wherein the biometric authentication includes one or more of afingerprint authentication, an iris pattern authentication, a heartbeatauthentication, and a vein pattern identification; wherein the veinpattern identification is performed using scanning of one or more of thefollowing: a palm vein pattern, a wrist vein pattern, a hand veinpattern, a leg vein pattern, a foot vein pattern, a neck vein pattern,and a head vein pattern; wherein the fingerprint authentication includesscanning fingerprints swiped across one or more or the following: ascreen of the mobile and wearable device, a button of the mobile andwearable device, and a rear panel of the mobile and wearable device. 13.The system of claim 8, wherein the payment receiving transaction and thepayment sending transaction are performed using a near fieldcommunication (NFC), wherein the NFC is used to pair the mobile andwearable device and a merchant device by bringing the mobile andwearable device into proximity to the merchant device, wherein themobile and wearable device and the merchant device are connected to acloud network, wherein the financial data and authorizing dataassociated with the user are stored in the cloud network, wherein uponpairing the mobile and wearable device with the merchant device aBluetooth connection between the mobile and wearable device and themerchant device is established, wherein the payment receivingtransaction and the payment sending transaction include at least apear-to-pear transaction.
 14. The system of claim 8, wherein theprocessor is further operable to receive, based on the determining thepayment transaction type which the user intends to perform, data of apayment card associated with the user, wherein the data of the paymentcard are received by scanning the payment card, the payment card beingscanned by a camera of the mobile and wearable device by positioning thepayment card in proximity to camera of the mobile and wearable device,wherein the payment card is associated with one or more of thefollowing: a bank account of the user and a virtual currency account ofthe user, wherein the bank account of the user and the virtual currencyaccount of the user are linked to a mobile and wearable device number.15. The system of claim 14, wherein the processor is further operable tostore the data of the payment card into a cloud network, wherein thedata of the payment card are stored in the cloud network as a token. 16.The system of claim 8, wherein the processor is further operable toreceive product data based on scanning of the product data by the mobileand wearable device associated with the user, the product data beingassociated with one or more products; calculate a total price for theone or more products; and receive merchant data, wherein the merchantdata are received by scanning a code associated with the merchant,wherein a scanned code associated with the merchant includes at least aQuick Response (QR) code associated with the merchant, wherein theQR-code associated with the merchant is stored in the mobile andwearable device of the user, wherein the OR-code associated with themerchant encodes at least a merchant account number.
 17. The system ofclaim 16, wherein the processor is further operable to: determine thatthe total price for the one or more products exceeds a predeterminedprice; and based on the determining, send a notification to a merchant,wherein the payment sending transaction includes sending a payment froma phone account of the user to a merchant account.
 18. The system ofclaim 8, wherein the payment receiving transaction and the paymentsending transaction are performed using pairing the mobile and wearabledevice and a merchant device using a reader, the reader being connectedto the merchant device and plugged into the mobile and wearable device.19. A system for performing transactions of a customer using a mobileand wearable device using the system comprising: the mobile and wearabledevice comprising a processor configured to: control reading productcodes of corresponding products using the mobile and wearable device,wherein merchant identification information is encoded into each of theproduct codes and extracted by the mobile and wearable device, andwherein the product codes correspond to products sold by differentmerchants having different corresponding merchant identificationinformation encoded therein; provide, via a customer interface of themobile and wearable device, merchant identification information, inaccordance with a payment processing system comprising a plurality ofthe merchants, the merchant identification information identifying amerchant in the payment processing system and corresponding merchantaccount; transmit customer identification information of the customer tothe payment processing system and the product codes to the paymentprocessing system; subsequent to the transmissions, retrieve of customerpayment information associated with the customer using the customeridentification information and the merchant identification informationby the payment processing system, the customer payment informationcorresponding to the customer payment account maintained at the paymentprocessing system associated with the merchant and further including aname of the customer, a customer account number of a financial account,and an amount of available funds; based on the customer identificationinformation and the merchant identification information, retrievecustomer records by the payment processing system, the customer recordsbeing maintained at the payment processing system, the customer recordsincluding at least discount information associated with the customer andloyalty program information associated with the customer; in response tothe transmitting transmissions and the retrieving, generate a barcodeencoding the customer payment information, merchant data, and thecustomer records specific to the merchant, said barcode generated usingthe merchant identification information and the customer identificationinformation and send said barcode to the mobile and wearable device;display the barcode on a screen of the mobile device, wherein thedisplayed barcode is scanned by a barcode scanner at a checkout counterof the payment processing system; and in response to the scanning,control the transfer payment from the customer payment account to eachof the merchant accounts corresponding to the merchant identificationinformation encoded into the product codes; control transmission of thetransactions and barcode to a point of sale device (POS), payee device,and another mobile and wearable device using Bluetooth Low Energy (BLE);the processor being further configured to: provide, in response to thereceiving of the payment information and authentication of the customer,a unique code encoding account information and a payment amount and ahaptic control, wherein the haptic control comprises a graphic image asa one touch button, shown on a display of the mobile and wearable deviceoverlapping other visual elements on the display, the haptic controlproviding mode selection elements associated with a payment mode, amessaging mode, a calling mode, and a multimedia capture mode, whereinthe haptic control is compatible with other programs installed on themobile and wearable device associated with the payment mode, themessaging mode, the calling mode, and the multimedia capture mode, thehaptic control facilitating online transactions not completed at thecheckout counter; superimpose, the haptic control on the display of themobile and wearable device on top of all content displayable of themobile and wearable device from the other programs, and using the hapticcontrol within the other programs to facilitate at least one ofperforming payments, messaging, and calling associated with the paymentmode, the messaging mode, the calling mode, and the multimedia capturemode of the mobile and wearable device; receive, a selection of thepayment mode via the mode selection elements of the haptic control fromthe customer, wherein the selection of the payment mode includes asingle touching of the mode selection elements associated with thepayment mode; upon the selection, automatically extract, context from atleast one of the other installed programs from the display of the mobileand wearable device, wherein the context comprises one or more of apayment recipient, a payment account, a sender account, and a paymentamount extracted from a web page, an application screen, or a message inview on the display; includes a web page, an application screen, or amessage in view on the display; and based on the context, automaticallydetermine, by the processor, a payment transaction type which thecustomer intends to perform, wherein the payment transaction typeincludes a payment receiving transaction and a payment sendingtransaction; when the determined payment transaction type is the paymentreceiving transaction, automatically send a transaction request to afinancial institution without requesting financial information,authorizing, or confirmations, wherein the transaction requestassociated with the payment receiving transaction includes at least theunique code, and receiving a payment from the financial institution,wherein subsequent to the selection of the payment mode, the paymentreceiving transaction is automatically performed with no further inputby the customer after the selection; when the determined paymenttransaction type is the payment sending transaction, calculate, adeposit amount associated with the payment sending transaction relatedto the customer and send a transaction request associated with thepayment sending transaction to the financial institution, wherein thetransaction request associated with the payment sending transactionincludes at least the unique code, wherein the deposit amount amounts toa predetermined percent from the payment amount, and wherein the depositamount is associated with the mobile payment account of the customer,and send a payment from the customer to the financial institution,wherein subsequent to the selection of the payment mode, the paymentsending transaction is automatically performed with no further input bythe customer after the selection; receive, a notification about afurther payment sending transaction of the customer via the mobilepayment service, the notification including at least the unique code anda payment amount of the further payment sending transaction; provide atleast one of a compensation, a rebate, a cashback, and a reward from thedeposit amount to the customer, the at least one of the compensation,the rebate, the cashback, and the reward being associated with thepayment amount associated with the further payment sending transactionand not associated with the payment sending transaction, wherein the atleast one of the compensation, the rebate, the cashback, and the rewardamounts to the predetermined percent from the payment amount; receive aselection of the messaging mode via the mode selection elements of thehaptic control from the customer, wherein the selection of the messagingmode includes a single touching of the mode selection elementsassociated with the messaging mode; when the selection of the messagingmode is received, provide, by the processor, a messaging interface onthe display of the mobile and wearable device to enable the customer toprovide, via the messaging interface, a message and a selection of arecipient, the selection of the messaging mode being performed viatouching the mode selection elements associated with the messaging modeby the customer; upon receipt of the message and the selection of therecipient, send the message to the recipient via a data network; receivea selection of the calling mode via the mode selection elements of thehaptic control from the customer, wherein the selection of the callingmode includes a single touching of the mode selection elementsassociated with the calling mode; when a selection of the calling modeis received, provide a calling interface on the display of the mobileand wearable device, to enable the customer to provide, via the callinginterface, a call recipient, the selection of the calling mode beingperformed via touching the mode selection elements associated with thecalling mode by the customer; upon receipt of the call recipient,perform a call with the call recipient via the data network; and when aselection of the multimedia capture mode is received, initiate one ormore sensors to capture multimedia; analyze the single touch todetermine a duration of the single touch, and based on the analysis,determine a type of multimedia to be recorded, wherein the type ofmultimedia includes an image and a video recording, and record thecaptured multimedia to the database.
 20. The system of claim 19, whereinthe one-touch button is integrated with at least one mobile applicationassociated with the mobile and wearable device, a point of sale device,a currency token service, and electronic payment card.
 21. The system ofclaim 19, wherein the at least one mobile application is integrated intoa software development kit and an operating system of the mobile andwearable device, wherein the operating system is selected from a groupcomprising: iOS, Android, and Windows Phone, wherein, upon launching ofthe at least one mobile application by the user, the user is prompted tolog in and asked to provide a consent that the at least one mobileapplication initiates future payments on behalf of the user, whereinduring further purchases the at least one mobile application is launchedby default without a need for a further action from the user to initiatelaunching of the at least one mobile application, the further actionincluding entering a login and a password by the user, wherein the atleast one mobile application is associated with performing payments andbuying products or services in the Internet.
 22. The system of claim 21,wherein upon launching of the at least one mobile application by theuser, a list of payment cards is provided for selection by the user, thepayment cards being associated with one or more of the following: a bankaccount, a bank mobile account, a service provider account, a digitalcurrency, a universal national currency token interface, a nationaldigital currency, and an electric payment card; wherein upon theselection, a token is sent to the mobile and wearable device, the tokenbeing associated with a selected payment card, wherein further paymentsare performed using the token.
 23. The system of claim 19, wherein apayment receiving transaction and a payment sending transaction areperformed using an NFC, wherein the NFC is used to pair the mobile andwearable device and a merchant device by bringing the mobile andwearable device into proximity to the merchant device, wherein themobile and wearable device and the merchant device are connected to acloud network, wherein the financial data and authorizing dataassociated with the user are stored in the cloud network, wherein uponpairing the mobile and wearable device with the merchant device aBluetooth connection between the mobile and wearable device and themerchant device is established, wherein the payment receivingtransaction and the payment sending transaction include at least apeer-to-peer transaction.